Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1741

reference: 168-tree-1
name: 1741
tree-preservation-order: undefined
168-tpo-1
uprn: 10013681107
address-text: Street Record, Orchid Drive, Emsworth
point: POINT (-0.935302 50.862642)
geometry: MULTIPOLYGON (((-0.935217 50.862633,-0.935221 50.862650,-0.935232 50.862665,-0.935251 50.862677,-0.935275 50.862685,-0.935301 50.862688,-0.935327 50.862686,-0.935351 50.862678,-0.935370 50.862666,-0.935383 50.862651,-0.935387 50.862635,-0.935384 50.862618,-0.935372 50.862603,-0.935353 50.862591,-0.935330 50.862583,-0.935303 50.862580,-0.935277 50.862582,-0.935253 50.862590,-0.935234 50.862602,-0.935221 50.862617,-0.935217 50.862633)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL